X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C9346D.2EA0B1D1@onstor-exch02.onstor.net>; Wed, 22 Oct 2008 10:39:49 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C9346D.2EA0B1D1"
Content-class: urn:content-classes:message
Subject: RE: Test Harness Changes
Date: Wed, 22 Oct 2008 10:39:49 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E083218BB@onstor-exch02.onstor.net>
In-Reply-To: <4D00E2D9-FDBD-41D8-9C0A-0D7B67E428CA@onstor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Test Harness Changes
Thread-Index: Ackz7n5b4EjTo8fITfWD1FN8aPWdnAAfkdtA
From: "Jan Seidel" <jan.seidel@onstor.com>
To: "Ian Brown" <ian.brown@onstor.com>,
	"YiFeng Liu" <yifeng.liu@onstor.com>,
	"Damon Wong" <damon.wong@onstor.com>
Cc: "dl-Design Review" <dl-designreview@onstor.com>,
	"Raj Kumar" <raj.kumar@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9346D.2EA0B1D1
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Ian,

=20

I updated the document=20

<\\mightydog\Program
Management\Kegg\Automation\test_harness_design_doc\DesignSpec-test_harne
ss_framework.doc
<file:///\\mightydog\Program%20Management\Kegg\Automation\test_harness_d
esign_doc\DesignSpec-test_harness_framework.doc> >

according to your comments.

=20

I tracked my changes so it should be easy for you to see what I changed.

=20

Please let me know if that answers your questions.

=20

Regards,

Jan

=20

=20

=20

________________________________

From: Ian Brown=20
Sent: Tuesday, October 21, 2008 7:33 PM
To: Jan Seidel; YiFeng Liu; Damon Wong
Cc: dl-Design Review; Raj Kumar
Subject: Re: Test Harness Changes

=20

Test Category Support.  (Damon)

=20

- shouldn't do categories that relate to test director unless we can
have our tests automatically populate test director with results.   My
take is that it would be better to use a different database instead of
Test Director, in which case we don't need to make these changes.

=20

If you do want categories in the test descriptions, then you should
create new test functions that take these as arguments (i.e. ok(), is()
etc...), and make the arguments required.   But I'm not in favor of
this.

=20

=20

Test Config Merge  (YiFeng)

=20

- in part 3, the "test harness root' should be considered to be the
'test/' directory.

- part 4 - don't add a new API, use test_config().  you can easily find
which directories have more than one test_config.yaml files going up the
tree in our current t/...  tree.  from there you can see of those
limited cases which ones will overwrite values in a way that will break
tests.  But frankly I do not think this is likely because the more
specific test_config.yaml will overwrite any setting from a lower
directory, so any config data returned from test_config() would be a
superset of what was there before, likely all tests would not check any
values that weren't already there so this isn't a problem.  So do a
little home work to see what might break, fix it, and then there's no
need for a new API.

- part 5 - put your tests for this module under t/...=20

=20

=20

Test Harness Framework (parallel runtests)  (Jan)

=20

- part 2 - it is never stated what the "timeout problem" is, and
therefore why it needs to be changed.  It should clearly say what the
timeout problem is.

- part ? (GatewayMonitor)  -- what happens if there is no gateway listed
in the available_resources_config.yaml?  what if we're running
test/t/runtests/... tests and we don't need a gateway?  will it still
try to log into a gateway?

- part 5.1.4 -- What's the problem?  Why must everything use
wait_time()?  I guess I'm again just wondering what the problem is, not
that there is a problem.

=20

Test Result Report (YiFeng)

=20

- 3.4.1 is not acceptable 3.4.2 is the way to go.  Often we write tests
that exit early by dying to indicate failure.  this would mess that
functionality up.

- 4.1.1 -- why not have a level before this one (1) that is the same a
perl's 'prove'  which prints out the file name and then some dots
............... then then number of the test being run, and any failed
test shows which test failed.  Basically if tests pass you don't do
anything but show which file you are running, but when you fail a test,
you print out the whole output of the error diagnostics.

- 4.2 & 4.3 & 5.1--  You should look at using Lod::Dispatch::Config for
storing results, and you might look at using the email plugin for
sending email plugins.  For 5.1 you could use a special $logger that
sent that debugging to "somewhere".

- 5.1 -- you don't say what you propose to implement.  you need to pick
something.  you can discuss the design tradeoffs.  But remember this is
a design document, it should give the design of what is actually going
to be done.   --- if you're going to do what prove does, you are going
to have to output the test number after each test is run, or the failure
of the tests.  I think it is good to output stuff as the tests go along,
this lets the user know what's going on.    Also if you use
Log::Dispatch::Config, you can log things as it goes too, so this should
make things easier for you. =20

=20

Windows support (Damon)

=20

- 5.2 - why are bash shells left around?  you need to explain this.
where are they left, on the cygwin machine? =20

- 5.2 - regarding disconnecting, what if the test script dies.  what do
you do then?  How do you clean up shares that are mounted on the windows
client.

- 5.3.4 & 5.3.5  -- I dont' see the difference.  Please explain what's
different between these two APIs.

=20

Vsvr Handling (Damon)

=20

- 4.2 -- why will the vsvr with the highest number be chosen?

- 5.1 - why does there need to be a "new" module for handling the
creation of vsvrs?

- 4 - are policy values case sensitive?  all caps?  first letter
capitalized?  --- cause you are not consistent in this document.

- 5.1 - why is the 'vsvr_policy' a list element in the test_config.yaml?
what does the yaml look like when  you want specify a particular vsvr
name?

- 5.2 - I don't understand what's trying to be said in this section.  I
think your english isn't clear enough for me to understand.

- 5.1 - why do we need a RUNTESTS file?  why isn't it suffixed with
'.yaml'?  Where is it going to be stored?

- 5.3.1 - 'grep the vsvr name for testing'  -- grep from where?

- 5.3.1 - a "vsvr with the highest number" -- highest number of what?

- 5.3.2 - "ONStor::Expect::GW::Nfxsh::Testutils::setup::test::vsvr()"
-- do you really mean that?  or do you mean
"ONStor::Expect::GW::Nfxsh::Testutils::setup_test_vsvr()" ?

- 5.3.2 - how are you going to get the PID of runtests -- especially if
the *.t test is not run with runtests

=20

- The writing/english in this doc is very poor. It takes me a long time
to get through what you have written and then I still don't understand
parts of it.  Did you proof read your doc?  If you did, then you should
probably have someone who is better at english help you with it before
you send it out for wider review as your design docs take me 4 to 5
times as much time to get through than the others in this batch.

-  There are a lot of problems here.  proof read this doc before I
review it again (including addressing comments).

=20

=20

=20

----  Ian  O_o

=20

=20

=20

=20

On Oct 11, 2008, at 7:47 AM, Raj Kumar wrote:

=20

Hi,

=20

Attached the design documents for various Test Harness requirements for
Test Automation. Can we have your comments by 10/15?

=20

Thanks.

=20

________________________________

From: Jan Seidel
Sent: Fri 10/10/2008 6:22 PM
To: Raj Kumar; Damon Wong; YiFeng Liu; Sandrine Boulanger; Jan Seidel
Cc: Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

Hi,

Here are our design specification documents.

They correspond to the priority 1 requirements that were initially
identified. Some documents cover multiple of these items, here is a
mapping:

DesignSpec-test_harness_framework.doc:
- General Framework changes
- Stop on error
- Detect when there's a crash
- Fix problems with timeouts

DesignSpec-category_support.doc:
- Run smoke, core, full set of tests

DesignSpec-test_result_report.doc:
- Getting a list of results (pass/fail) for each test case
- Fix the bug for having wrongly reported test results
- Modify and add verbosity level for test report
- Add email function

DesignSpec-vsvr_handling.doc:
- Handling vsvrs, use unique volumes for each test
- Run multiple st of tests on the same NAS Gateway in parallel

DesignSpec-test_config_merge.doc:
- Merge test_config.yaml files down the directory tree

DesignSpec-windows_support.doc:
- Ability to kick off tests on Windows clients

The only item currently missing is the "universal way to create data
sets" document. There is some additional work required to collect all
requirements for this task.

Regards,
Jan


-----Original Message-----
From: Raj Kumar
Sent: Wednesday, October 01, 2008 12:34 PM
To: Damon Wong; YiFeng Liu; Sandrine Boulanger; Jan Seidel
Cc: Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

Great. Thanks.

-----Original Message-----
From: Damon Wong
Sent: Wednesday, October 01, 2008 12:09 PM
To: YiFeng Liu; Sandrine Boulanger; Jan Seidel; Raj Kumar
Cc: Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

We have done meeting and this is the distribution of the tasks:

damon

-----Original Message-----
From: YiFeng Liu
Sent: Wednesday, October 01, 2008 11:10 AM
To: Sandrine Boulanger; Jan Seidel; Raj Kumar; Damon Wong
Cc: Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

Sorry about the implicit "we", I actually meant Jan, Damon and me, but
we definitly will keep you guys updated.


-----Original Message-----
From: Sandrine Boulanger
Sent: Wed 10/1/2008 10:58 AM
To: YiFeng Liu; Jan Seidel; Raj Kumar; Damon Wong
Cc: Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

Go ahead. Raj, Amit and I will be in meetings from 2 to 6PM, but the
three of you should meet and send us the results.

-----Original Message-----
From: YiFeng Liu
Sent: Wednesday, October 01, 2008 10:38 AM
To: Jan Seidel; Raj Kumar; Damon Wong
Cc: Sandrine Boulanger; Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

We can meet sometime today to discuss the details regarding the design
and then start working the distributed items afterward to save duplicate
efforts.


-----Original Message-----
From: Jan Seidel
Sent: Tue 9/30/2008 6:18 PM
To: Raj Kumar; YiFeng Liu; Damon Wong
Cc: Sandrine Boulanger; Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

Ok, shall Damon, YiFeng and me start doing this or shall we first meet
all together again?

Regards,
Jan

-----Original Message-----
From: Raj Kumar
Sent: Tuesday, September 30, 2008 6:17 PM
To: YiFeng Liu; Jan Seidel; Damon Wong
Cc: Sandrine Boulanger; Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

Let us start putting together a design document for the proposed
changes.

Thanks.

-----Original Message-----
From: YiFeng Liu
Sent: Tuesday, September 30, 2008 12:14 PM
To: Raj Kumar; Jan Seidel; Damon Wong
Cc: Sandrine Boulanger; Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

We have not yet decided on who is working on which part, since there are
many design questions are still open to discussion.

-----Original Message-----
From: Raj Kumar
Sent: Tue 9/30/2008 9:38 AM
To: Jan Seidel; YiFeng Liu; Damon Wong
Cc: Sandrine Boulanger; Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

Have you guys decided about who is going to work on these different
tasks?

-----Original Message-----
From: Raj Kumar
Sent: Tuesday, September 30, 2008 7:22 AM
To: Jan Seidel; YiFeng Liu; Damon Wong
Cc: Sandrine Boulanger; Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

Nicely done, thanks. I will update the schedule based on this.

-----Original Message-----
From: Jan Seidel
Sent: Monday, September 29, 2008 4:46 PM
To: Raj Kumar; YiFeng Liu; Damon Wong
Cc: Sandrine Boulanger; Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

Hi,

Here is the document with our scoping.

Regards,
Jan

-----Original Message-----
From: Raj Kumar
Sent: Monday, September 29, 2008 9:42 AM
To: Jan Seidel; YiFeng Liu; Damon Wong
Cc: Sandrine Boulanger; Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

Excellent. Thanks.

-----Original Message-----
From: Jan Seidel
Sent: Monday, September 29, 2008 9:29 AM
To: Raj Kumar; YiFeng Liu; Damon Wong
Cc: Sandrine Boulanger; Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

Hi Raj,

we split up the priority 1 requirements and planned to meet again this
afternoon, so we will probably have the scoping then.

Regards,
Jan


-----Original Message-----
From: Raj Kumar
Sent: Mon 9/29/2008 9:10 AM
To: Raj Kumar; Jan Seidel; YiFeng Liu; Damon Wong
Cc: Sandrine Boulanger; Amit Bothra; Jobi Ariyamannil
Subject: RE: Requirements with priorities

Hi,

When do you think we will have the scoping done for these?

Thanks.

_____________________________________________
From: Raj Kumar
Sent: Friday, September 26, 2008 4:21 PM
To: Jan Seidel; YiFeng Liu; Damon Wong
Cc: Sandrine Boulanger; Amit Bothra; Jobi Ariyamannil
Subject: Requirements with priorities

Jan , YiFeng, Damon,

The below document contains the list of the requirements and their
agreed upon priorities. Can you please go over the priority-1
requirements and scope them? Per requirement we will need,

*       Sub tasks and their estimates in man days
*       Man days estimate per requirement

\\mightydog\qe\projects\kegg\TestAutomation\TestHarness_Requirements.xls

Thanks







<DesignSpec-category_support.doc><DesignSpec-test_config_merge.doc><Desi
gnSpec-test_harness_framework.doc><DesignSpec-test_result_report.doc><De
signSpec-vsvr_handling.doc><DesignSpec-windows_support.doc>

=20


------_=_NextPart_001_01C9346D.2EA0B1D1
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:navy;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dnavy style=3D'word-wrap: =
break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi =
Ian,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I updated the document =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&lt;<a
href=3D"file:///\\mightydog\Program%20Management\Kegg\Automation\test_har=
ness_design_doc\DesignSpec-test_harness_framework.doc">\\mightydog\Progra=
m
Management\Kegg\Automation\test_harness_design_doc\DesignSpec-test_harnes=
s_framework.doc</a>&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>according to your =
comments.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I tracked my changes so it should =
be easy
for you to see what I changed.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Please let me know if that answers =
your
questions.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Regards,<o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Jan<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Ian =
Brown <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, October =
21, 2008
7:33 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Jan Seidel; YiFeng =
Liu; <st1:PersonName
w:st=3D"on">Damon Wong</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> dl-Design Review; Raj =
Kumar<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: Test Harness =
Changes</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><span class=3Dapple-style-span><b><u><font size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-weight:bold'>Test
Category Support</span></font></u></b></span>. =
&nbsp;(Damon)<o:p></o:p></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- shouldn't do categories that relate to test director unless we =
can
have our tests automatically populate test director with results. &nbsp; =
My
take is that it would be better to use a different database instead of =
Test
Director, in which case we don't need to make these =
changes.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>If you do want categories in the test descriptions, then you =
should
create new test functions that take these as arguments (i.e. ok(), is()
etc...), and make the arguments required. &nbsp; But I'm not in favor of =
this.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><span class=3Dapple-style-span><b><u><font size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-weight:bold'>Test
Config Merge</span></font></u></b></span> &nbsp;(YiFeng)<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- in part 3, the &quot;test harness root' should be considered =
to be
the 'test/' directory.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- part 4 - don't add a new API, use test_config(). &nbsp;you can =
easily
find which directories have more than one test_config.yaml files going =
up the
tree in our current t/... &nbsp;tree. &nbsp;from there you can see of =
those
limited cases which ones will overwrite values in a way that will break =
tests.
&nbsp;But frankly I do not think this is likely because the more =
specific
test_config.yaml will overwrite any setting from a lower directory, so =
any
config data returned from test_config() would be a superset of what was =
there
before, likely all tests would not check any values that weren't already =
there
so this isn't a problem. &nbsp;So do a little home work to see what =
might
break, fix it, and then there's no need for a new =
API.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- part 5 - put your tests for this module under =
t/...&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><span class=3Dapple-style-span><b><u><font size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-weight:bold'>Test
Harness Framework</span></font></u></b><u> (parallel =
runtests)</u></span>
&nbsp;(Jan)<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- part 2 - it is never stated what the &quot;timeout =
problem&quot; is,
and therefore why it needs to be changed. &nbsp;It should clearly say =
what the
timeout problem is.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- part ? (GatewayMonitor) &nbsp;-- what happens if there is no =
gateway
listed in the available_resources_config.yaml? &nbsp;what if we're =
running
test/t/runtests/... tests and we don't need a gateway? &nbsp;will it =
still try
to log into a gateway?<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- part 5.1.4 -- What's the problem? &nbsp;Why must everything =
use
wait_time()? &nbsp;I guess I'm again just wondering what the problem is, =
not
that there is a problem.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><span class=3Dapple-style-span><b><u><font size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-weight:bold'>Test
Result Report</span></font></u></b></span> (YiFeng)<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 3.4.1 is not acceptable 3.4.2 is the way to go. &nbsp;Often we =
write
tests that exit early by dying to indicate failure. &nbsp;this would =
mess that
functionality up.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 4.1.1 -- why not have a level before this one (1) that is the =
same a
perl's 'prove' &nbsp;which prints out the file name and then some dots
............... then then number of the test being run, and any failed =
test
shows which test failed. &nbsp;Basically if tests pass you don't do =
anything
but show which file you are running, but when you fail a test, you print =
out the
whole output of the error diagnostics.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 4.2 &amp; 4.3 &amp; 5.1-- &nbsp;You should look at using
Lod::Dispatch::Config for storing results, and you might look at using =
the
email plugin for sending email plugins. &nbsp;For 5.1 you could use a =
special
$logger that sent that debugging to =
&quot;somewhere&quot;.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 5.1 -- you don't say what you propose to implement. &nbsp;you =
need to
pick something. &nbsp;you can discuss the design tradeoffs. &nbsp;But =
remember
this is a design document, it should give the design of what is actually =
going
to be done. &nbsp; --- if you're going to do what prove does, you are =
going to
have to output the test number after each test is run, or the failure of =
the
tests. &nbsp;I think it is good to output stuff as the tests go along, =
this
lets the user know what's going on. &nbsp; &nbsp;Also if you use
Log::Dispatch::Config, you can log things as it goes too, so this should =
make
things easier for you. &nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><span class=3Dapple-style-span><b><u><font size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-weight:bold'>Windows
support</span></font></u></b></span> (Damon)<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 5.2 - why are bash shells left around? &nbsp;you need to =
explain
this. &nbsp;where are they left, on the cygwin machine? =
&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 5.2 - regarding disconnecting, what if the test script dies.
&nbsp;what do you do then? &nbsp;How do you clean up shares that are =
mounted on
the windows client.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 5.3.4 &amp; 5.3.5 &nbsp;-- I dont' see the difference. =
&nbsp;Please
explain what's different between these two =
APIs.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><b><u><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt;font-weight:bold'>Vsvr =
Handling</span></font></u></b>&nbsp;(Damon)<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 4.2 -- why will the vsvr with the highest number be =
chosen?<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 5.1 - why does there need to be a &quot;new&quot; module for =
handling
the creation of vsvrs?<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 4 - are policy values case sensitive? &nbsp;all caps? =
&nbsp;first
letter capitalized? &nbsp;--- cause you are not&nbsp;consistent&nbsp;in =
this
document.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 5.1 - why is the 'vsvr_policy' a list element in the
test_config.yaml? &nbsp;what does the yaml look like when &nbsp;you want
specify a particular vsvr name?<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 5.2 - I don't understand what's trying to be said in this =
section.
&nbsp;I think your english isn't clear enough for me to =
understand.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 5.1 - why do we need a RUNTESTS file? &nbsp;why isn't it =
suffixed
with '.yaml'? &nbsp;Where is it going to be =
stored?<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 5.3.1 - 'grep the vsvr name for testing' &nbsp;-- grep from =
where?<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 5.3.1 - a &quot;vsvr with the highest number&quot; -- highest =
number
of what?<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- 5.3.2 - &quot;</span></font><span =
class=3Dapple-style-span><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>ONStor::Expect::GW::Nfxsh::T=
estutils::setup::test::vsvr()&quot;
&nbsp;-- do you really mean that? &nbsp;or do you mean
&nbsp;&quot;ONStor::Expect::GW::Nfxsh::Testutils::setup_test_vsvr()&quot;=
 ?</span></font></span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span class=3Dapple-style-span><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>- 5.3.2 - how are you going =
to get
the PID of runtests -- especially if the *.t test is not run with =
runtests</span></font></span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><span class=3Dapple-style-span><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>- The writing/english in =
this doc is
very poor. It takes me a long time to get through what you have written =
and
then I still don't understand parts of it. &nbsp;Did you proof read your =
doc?
&nbsp;If you did, then you should probably have someone who is better at
english help you with it before you send it out for wider review as your =
design
docs take me 4 to 5 times as much time to get through than the others in =
this
batch.</span></font></span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span class=3Dapple-style-span><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>- &nbsp;There are a lot of =
problems
here. &nbsp;proof read this doc before I review it again (including =
addressing
comments).</span></font></span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><span class=3Dapple-style-span><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>---- &nbsp;Ian =
&nbsp;O_o</span></font></span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>On Oct 11, 2008, at 7:47 AM, Raj Kumar =
wrote:<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div id=3DidOWAReplyText26033>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Hi,</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Attached the design documents for various Test =
Harness requirements
for Test Automation. Can we have your comments by =
10/15?</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks.</span></font><o:p></o:p></p>

</div>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Jan
Seidel<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Fri 10/10/2008 6:22 =
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Raj Kumar; =
<st1:PersonName
w:st=3D"on">Damon Wong</st1:PersonName>; YiFeng Liu; <st1:PersonName =
w:st=3D"on">Sandrine
 Boulanger</st1:PersonName>; Jan Seidel<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Amit Bothra; =
<st1:PersonName
w:st=3D"on">Jobi Ariyamannil</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Requirements =
with
priorities</span></font><o:p></o:p></p>

</div>

<div>

<p style=3D'margin-bottom:12.0pt'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>Hi,<br>
<br>
Here are our design specification documents.<br>
<br>
They correspond to the priority 1 requirements that were initially =
identified.
Some documents cover multiple of these items, here is a mapping:<br>
<br>
DesignSpec-test_harness_framework.doc:<br>
- General Framework changes<br>
- Stop on error<br>
- Detect when there's a crash<br>
- Fix problems with timeouts<br>
<br>
DesignSpec-category_support.doc:<br>
- Run smoke, core, full set of tests<br>
<br>
DesignSpec-test_result_report.doc:<br>
- Getting a list of results (pass/fail) for each test case<br>
- Fix the bug for having wrongly reported test results<br>
- Modify and add verbosity level for test report<br>
- Add email function<br>
<br>
DesignSpec-vsvr_handling.doc:<br>
- Handling vsvrs, use unique volumes for each test<br>
- Run multiple st of tests on the same NAS Gateway in parallel<br>
<br>
DesignSpec-test_config_merge.doc:<br>
- Merge test_config.yaml files down the directory tree<br>
<br>
DesignSpec-windows_support.doc:<br>
- Ability to kick off tests on Windows clients<br>
<br>
The only item currently missing is the &quot;universal way to create =
data
sets&quot; document. There is some additional work required to collect =
all
requirements for this task.<br>
<br>
Regards,<br>
Jan<br>
<br>
<br>
-----Original Message-----<br>
From: Raj Kumar<br>
Sent: Wednesday, October 01, 2008 12:34 PM<br>
To: <st1:PersonName w:st=3D"on">Damon Wong</st1:PersonName>; YiFeng Liu; =
<st1:PersonName
w:st=3D"on">Sandrine Boulanger</st1:PersonName>; Jan Seidel<br>
Cc: Amit Bothra; <st1:PersonName w:st=3D"on">Jobi =
Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
Great. Thanks.<br>
<br>
-----Original Message-----<br>
From: <st1:PersonName w:st=3D"on">Damon Wong</st1:PersonName><br>
Sent: Wednesday, October 01, 2008 12:09 PM<br>
To: YiFeng Liu; <st1:PersonName w:st=3D"on">Sandrine =
Boulanger</st1:PersonName>;
Jan Seidel; Raj Kumar<br>
Cc: Amit Bothra; <st1:PersonName w:st=3D"on">Jobi =
Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
We have done meeting and this is the distribution of the tasks:<br>
<br>
damon<br>
<br>
-----Original Message-----<br>
From: YiFeng Liu<br>
Sent: Wednesday, October 01, 2008 11:10 AM<br>
To: <st1:PersonName w:st=3D"on">Sandrine Boulanger</st1:PersonName>; Jan =
Seidel;
Raj Kumar; <st1:PersonName w:st=3D"on">Damon Wong</st1:PersonName><br>
Cc: Amit Bothra; <st1:PersonName w:st=3D"on">Jobi =
Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
Sorry about the implicit &quot;we&quot;, I actually meant Jan, Damon and =
me,
but we definitly will keep you guys updated.<br>
<br>
<br>
-----Original Message-----<br>
From: <st1:PersonName w:st=3D"on">Sandrine =
Boulanger</st1:PersonName><br>
Sent: Wed 10/1/2008 10:58 AM<br>
To: YiFeng Liu; Jan Seidel; Raj Kumar; <st1:PersonName w:st=3D"on">Damon =
Wong</st1:PersonName><br>
Cc: Amit Bothra; <st1:PersonName w:st=3D"on">Jobi =
Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
Go ahead. Raj, Amit and I will be in meetings from 2 to 6PM, but the =
three of
you should meet and send us the results.<br>
<br>
-----Original Message-----<br>
From: YiFeng Liu<br>
Sent: Wednesday, October 01, 2008 10:38 AM<br>
To: Jan Seidel; Raj Kumar; <st1:PersonName w:st=3D"on">Damon =
Wong</st1:PersonName><br>
Cc: <st1:PersonName w:st=3D"on">Sandrine Boulanger</st1:PersonName>; =
Amit Bothra;
<st1:PersonName w:st=3D"on">Jobi Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
We can meet sometime today to discuss the details regarding the design =
and then
start working the distributed items afterward to save duplicate =
efforts.<br>
<br>
<br>
-----Original Message-----<br>
From: Jan Seidel<br>
Sent: Tue 9/30/2008 6:18 PM<br>
To: Raj Kumar; YiFeng Liu; <st1:PersonName w:st=3D"on">Damon =
Wong</st1:PersonName><br>
Cc: <st1:PersonName w:st=3D"on">Sandrine Boulanger</st1:PersonName>; =
Amit Bothra;
<st1:PersonName w:st=3D"on">Jobi Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
Ok, shall Damon, YiFeng and me start doing this or shall we first meet =
all
together again?<br>
<br>
Regards,<br>
Jan<br>
<br>
-----Original Message-----<br>
From: Raj Kumar<br>
Sent: Tuesday, September 30, 2008 6:17 PM<br>
To: YiFeng Liu; Jan Seidel; <st1:PersonName w:st=3D"on">Damon =
Wong</st1:PersonName><br>
Cc: <st1:PersonName w:st=3D"on">Sandrine Boulanger</st1:PersonName>; =
Amit Bothra;
<st1:PersonName w:st=3D"on">Jobi Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
Let us start putting together a design document for the proposed =
changes.<br>
<br>
Thanks.<br>
<br>
-----Original Message-----<br>
From: YiFeng Liu<br>
Sent: Tuesday, September 30, 2008 12:14 PM<br>
To: Raj Kumar; Jan Seidel; <st1:PersonName w:st=3D"on">Damon =
Wong</st1:PersonName><br>
Cc: <st1:PersonName w:st=3D"on">Sandrine Boulanger</st1:PersonName>; =
Amit Bothra;
<st1:PersonName w:st=3D"on">Jobi Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
We have not yet decided on who is working on which part, since there are =
many
design questions are still open to discussion.<br>
<br>
-----Original Message-----<br>
From: Raj Kumar<br>
Sent: Tue 9/30/2008 9:38 AM<br>
To: Jan Seidel; YiFeng Liu; <st1:PersonName w:st=3D"on">Damon =
Wong</st1:PersonName><br>
Cc: <st1:PersonName w:st=3D"on">Sandrine Boulanger</st1:PersonName>; =
Amit Bothra;
<st1:PersonName w:st=3D"on">Jobi Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
Have you guys decided about who is going to work on these different =
tasks?<br>
<br>
-----Original Message-----<br>
From: Raj Kumar<br>
Sent: Tuesday, September 30, 2008 7:22 AM<br>
To: Jan Seidel; YiFeng Liu; <st1:PersonName w:st=3D"on">Damon =
Wong</st1:PersonName><br>
Cc: <st1:PersonName w:st=3D"on">Sandrine Boulanger</st1:PersonName>; =
Amit Bothra;
<st1:PersonName w:st=3D"on">Jobi Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
Nicely done, thanks. I will update the schedule based on this.<br>
<br>
-----Original Message-----<br>
From: Jan Seidel<br>
Sent: Monday, September 29, 2008 4:46 PM<br>
To: Raj Kumar; YiFeng Liu; <st1:PersonName w:st=3D"on">Damon =
Wong</st1:PersonName><br>
Cc: <st1:PersonName w:st=3D"on">Sandrine Boulanger</st1:PersonName>; =
Amit Bothra;
<st1:PersonName w:st=3D"on">Jobi Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
Hi,<br>
<br>
Here is the document with our scoping.<br>
<br>
Regards,<br>
Jan<br>
<br>
-----Original Message-----<br>
From: Raj Kumar<br>
Sent: Monday, September 29, 2008 9:42 AM<br>
To: Jan Seidel; YiFeng Liu; <st1:PersonName w:st=3D"on">Damon =
Wong</st1:PersonName><br>
Cc: <st1:PersonName w:st=3D"on">Sandrine Boulanger</st1:PersonName>; =
Amit Bothra;
<st1:PersonName w:st=3D"on">Jobi Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
Excellent. Thanks.<br>
<br>
-----Original Message-----<br>
From: Jan Seidel<br>
Sent: Monday, September 29, 2008 9:29 AM<br>
To: Raj Kumar; YiFeng Liu; <st1:PersonName w:st=3D"on">Damon =
Wong</st1:PersonName><br>
Cc: <st1:PersonName w:st=3D"on">Sandrine Boulanger</st1:PersonName>; =
Amit Bothra;
<st1:PersonName w:st=3D"on">Jobi Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
Hi Raj,<br>
<br>
we split up the priority 1 requirements and planned to meet again this
afternoon, so we will probably have the scoping then.<br>
<br>
Regards,<br>
Jan<br>
<br>
<br>
-----Original Message-----<br>
From: Raj Kumar<br>
Sent: Mon 9/29/2008 9:10 AM<br>
To: Raj Kumar; Jan Seidel; YiFeng Liu; <st1:PersonName w:st=3D"on">Damon =
Wong</st1:PersonName><br>
Cc: <st1:PersonName w:st=3D"on">Sandrine Boulanger</st1:PersonName>; =
Amit Bothra;
<st1:PersonName w:st=3D"on">Jobi Ariyamannil</st1:PersonName><br>
Subject: RE: Requirements with priorities<br>
<br>
Hi,<br>
<br>
When do you think we will have the scoping done for these?<br>
<br>
Thanks.<br>
<br>
_____________________________________________<br>
From: Raj Kumar<br>
Sent: Friday, September 26, 2008 4:21 PM<br>
To: Jan Seidel; YiFeng Liu; <st1:PersonName w:st=3D"on">Damon =
Wong</st1:PersonName><br>
Cc: <st1:PersonName w:st=3D"on">Sandrine Boulanger</st1:PersonName>; =
Amit Bothra;
<st1:PersonName w:st=3D"on">Jobi Ariyamannil</st1:PersonName><br>
Subject: Requirements with priorities<br>
<br>
Jan , YiFeng, Damon,<br>
<br>
The below document contains the list of the requirements and their =
agreed upon
priorities. Can you please go over the priority-1 requirements and scope =
them?
Per requirement we will need,<br>
<br>
*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sub tasks and their estimates in =
man days<br>
*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Man days estimate per =
requirement<br>
<br>
\\mightydog\qe\projects\kegg\TestAutomation\TestHarness_Requirements.xls<=
br>
<br>
Thanks<br>
<br>
<br>
<br>
<br>
<br>
</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&lt;DesignSpec-category_support.doc&gt;&lt;DesignSpec-test_config=
_merge.doc&gt;&lt;DesignSpec-test_harness_framework.doc&gt;&lt;DesignSpec=
-test_result_report.doc&gt;&lt;DesignSpec-vsvr_handling.doc&gt;&lt;Design=
Spec-windows_support.doc&gt;<o:p></o:p></span></font></p>

</div>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C9346D.2EA0B1D1--
